Release 10.1A: OpenEdge Data Management:
DataServer for ORACLE

Starting the DataServer in the Explorer administration framework

The Progress Explorer administration framework administers only the server module (_orasrv in Windows and on UNIX) of the DataServer. After starting the server, start your OpenEdge client as you would in any remote DataServer configuration. The following sections describe how to run the DataServer in the Explorer administration framework in Windows and on UNIX.

In the Windows host

Use the Progress Explorer tool to run DataServer processes in the Windows host. Optionally you can use the command-line technique described in the "On the UNIX host" section. To configure the DataServer, see the "Configuring the DataServer in the Explorer administration framework" section. This section presents basic start, stop, and status check procedures for the DataServer.

To start the DataServer:

From the Progress Explorer’s left pane, select the ORACLE DataServer folder and double-click. The list of existing DataServer brokers for ORACLE appears in the right pane.
Select the DataServer broker you want to start and right-click. A pop-up menu appears.
Choose the Start option from the pop-up menu. The Status in the right pane changes to Running for that DataServer broker.

To check the status of a DataServer broker:

Select the DataServer broker and right-click.
Choose the Status option from the pop-up menu.

See the Progress Explorer online Help for more information the various Status tabs.

To stop the DataServer broker:

Select the DataServer broker and right-click.
Choose the Stop option from the pop-up menu. The Status in the right pane changes to Not Running for that DataServer broker.

For more information on using the Progress Explorer tool, see the online Help.

On the UNIX host

Use the Progress Explorer administration framework command-line interface to run DataServer processes on the UNIX host. To configure the DataServer, see the "Configuring the DataServer in the Explorer administration framework" section.

To start the DataServer broker, enter this command at the system prompt on the machine where the broker will run:

oraman -name broker-name -start

Where broker-name is the name you gave the broker when you configured it.

You can run the broker from a remote machine. In that case, you specify additional options that identify the remote host. For example:

oraman -name broker-name -start -host host-name -user user-name

where broker-name is the name you gave the broker when you configured it; host-name is the name of the host machine on which you want the broker to run; and user-name is the user ID of the system account under which the AdminServer is running. This account can be different from the one that owns the DataServer broker, which in turn can be different from the user profile you use to connect to the ORACLE database.

You can also use the oraman utility to check the status of a broker. To check the status of a broker, enter this command at the system prompt on the machine where the broker is running:

oraman -name broker-name -query

To stop the DataServer broker, enter this command at the system prompt on the machine where the broker will run:

oraman -name broker-name -stop

You can stop a broker on a remote machine by adding the -host and -user options.

See Appendix E, "DataServer Command Line Utilities and Startup Parameters," for a complete description.

On the client

After you have started the broker on the host machine, you can connect your UNIX or Windows client. Use the same parameters that you would use for connecting to the schema holder and ORACLE in a standard configuration. In addition:

Include the -Dsrv SVUB,1 parameter. This parameter allows you to connect to the broker administered by the Explorer.
Include the -DataService data–service parameter to connect through a NameServer to the broker. The value for data–service must specify a valid name from the DataService list registered to this NameServer as defined by your appServiceNameList entry in the broker properties file. If a default DataService has been defined for your broker instance, you can omit this parameter and connect using the default service.

For diagnostic purposes, it is acceptable to bypass the NameServer connection and connect directly to the broker instance. To do this, specify the reserved DataService name “none” or add the -DirectConnect parameter as follows:

-DataService none

Or

-DirectConnect

Set the -S parameter to one of the following:
The port number assigned to the controlling NameServer (when the -DataService value is not “none”) or the port number of the broker instance that you started in the Explorer (when the -DataService value is “none”).
The service name in your service file, \windows-install-dir\system32\drivers\etc\services in Windows or /etc/services on UNIX, whose associated port matches the port of the controlling NameServer (when the -DataService value is not “none”) or the broker instance that you started in the Explorer (when the -DataService value is “none”).
Set the -H parameter to the name of the machine where the NameServer and/or broker instance is running.

If you do not set the required -Dsrv SVUB,1 and optional -DataService data–service connection parameters as described in this section, the client is assumed to be configured for a standard OpenEdge broker and the -H and -S parameters are used to locate a Probroker executable on the appropriate host machine. By setting the SVUB parameter on, you redirect the -H and -S parameters to locate the appropriate NameServer and/or broker on the host machine.

The following example illustrates how to use these connection parameters for a client that connects to a NameServer:

CONNECT oraholder -db orademo -dt ORACLE -U bob -P bobpass -H host1 -S oraservice -DataService orabroker1 -Dsrv SVUB,1